Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

close connection when receiving unprotected ACKs for protected packets #810

Conversation

marten-seemann
Copy link
Contributor

@marten-seemann marten-seemann commented Oct 1, 2017

The TLS draft says in https://quicwg.github.io/base-drafts/draft-ietf-quic-tls.html#rfc.section.9.1.2:

Endpoints MUST NOT use an ACK frame in an unprotected packet to acknowledge packets that were protected by 0-RTT or 1-RTT keys. An endpoint MUST treat receipt of an ACK frame in an unprotected packet that claims to acknowledge protected packets as a connection error of type OPTIMISTIC_ACK.

The Loss Recovery draft currently says that unprotected packets containing ACKs for protected packets have to be ignored. This PR updates the Loss Recovery draft and makes it consistent with the TLS draft.

@ianswett ianswett merged commit 585d504 into quicwg:master Oct 1, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants